Inter-carrier messaging service providing phone number only experience

ABSTRACT

A phone number only messaging experience is provided in an Inter-Carrier Messaging System service. Subscriber to subscriber digital messages containing user data are routed between carrier&#39;s networks using an Inter-Carrier messaging module with appropriate MIN/carrier/carrier routing look-up capabilities. Digital messages containing user data (e.g., short messages, email, digital messages in general, etc.) may be sent to a subscriber in another carrier&#39;s network addressed only with a phone number. If the recipient is outside of the sender&#39;s carrier network, the Inter-Carrier messaging module of the Inter-Carrier service provider (ICSP) determines the appropriate carrier for the recipient, appends the appropriate syntax to the digital message containing user data to allow internet protocol (IP) or other standardized communication techniques between message service centers of the two carriers, and routes the digital message containing user data to the destination carrier. The recipient in the other carrier&#39;s network may reply back to the ICSP&#39;s sender using only the subscriber&#39;s directory number.

The present application is a continuation of U.S. patent applicationSer. No. 12/073,262, entitled “Inter-Carrier Messaging Service ProvidingPhone Number Only Experience,” filed on Mar. 3, 2008, now U.S. Pat. No.7,890,127, which in turn is a continuation of U.S. application Ser. No.11/359,586, entitled “Inter-Carrier Messaging Service Providing PhoneNumber Only Experience,” filed on Feb. 23, 2006, (now abandoned), whichin turn is a continuation of U.S. patent application Ser. No.11/130,256, entitled “Inter-Carrier Digital Message with User DataPayload Service Providing Phone Number Only Experience,” (as amended)filed on May 17, 2005, (now abandoned), which in turn is a continuationof U.S. patent application Ser. No. 10/720,343, filed on Nov. 25, 2003,entitled “Inter-Carrier Short Messaging Service Providing Phone NumberOnly Experience,” now U.S. Pat. No. 6,985,748, which in turn is acontinuation of U.S. patent application Ser. No. 09/985,032 filed onNov. 1, 2001, entitled “Inter-Carrier Short Messaging Service ProvidingPhone Number Only Experience”, now U.S. Pat. No. 6,658,260, which inturn claims priority from U.S. Provisional Application No. 60/316,973,filed Sep. 5, 2001, entitled “Internet Protocol (IP) Based Inter-CarrierMessaging Service”, the entirety of all of which are expresslyincorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to wireless carriers, Internet serviceproviders (ISPs), and information content delivery services/providers.More particularly, it relates to digital messaging services providedbetween different carriers and/or between subscribers in different airinterface standards.

2. Background of Related Art

We are now in what is called the information age. More than ever, theexchange of information, and the ability to do the same, has become animportant technical necessity of modern society. With the introductionand now wide usage of the Internet, and the advances intelecommunications, a variety of means for exchanging information haveproliferated to bring a great number of people together through theexchange of information.

In the early 1990s, as a result of the growing popularity of digitalwireless technology, a standard for digital wireless networks wasintroduced in Europe. That standard, now known as the global standardfor mobiles (GSM), included a service called short messaging service(SMS). One way in which information is exchanged is through shortmessages. A short message is typically a textual message, e.g., a pagingmessage, e-mail or a voice mail message passed to and/or from varioustypes of communication devices, e.g., cellular telephone handsets,telephones or computers with appropriate modems.

An SMS allows transmission of short messages, typically up to 160characters, to and from communication devices, e.g., cellular telephonehandsets, telephones or computers with appropriate modems. In NorthAmerica, the SMS is currently implemented on digital wireless/mobilenetworks, such as a PCS network based on the GSM standard, code divisionmultiple access (CDMA) and/or time division multiple access (TDMA)methods. Short message services are gaining in popularity, particularlyin the United States.

Short message services are advantageous over text based paging servicesbecause of the capability of bi-directional communication. Suchbi-directional communication allows, for example, notification to theoriginating device of the success or failure of the short messagedelivery.

Each SMS network typically includes a Short Message Service Center(SMSC) which acts as a store-and-forward mechanism providing guaranteeddelivery of short messages to a subscriber, even if the subscriber isinactive when the message was transmitted, by delivering the shortmessages once the subscriber becomes active. Delivery of all shortmessages is guaranteed regardless of whether or not the intendedsubscriber is “on-line” because the transmitted short message is storedwithin the one SMSC assigned to each intended subscriber, and deliveredto the intended subscriber from their assigned SMSC when the subscriberbecomes available.

A variety of services have been introduced using SMS networks including,for example, integrated electronic mail and fax, integrated paging,interactive banking, and information services such as stock quotes andairline schedule delivery.

In operation, an SMSC receives a short message from any source intendedto be delivered to a particular subscriber. When the intended subscriberis not available because, for example, it is turned off or is outside ofthe service area of the SMS network, the attempt to deliver the shortmessage at that time will fail. In this case, the short message will beretained in the SMSC assigned to that intended subscriber for a laterdelivery attempt. Thereafter, when the subscriber finally becomesavailable, e.g., is turned on or has moved into the service area of theSMS network, the relevant portions of the network (e.g., the mobileservicing center (MSC) and the home location register (HLR)) notify theSMSC to initiate delivery of the stored (i.e., previously failed) shortmessages.

FIG. 9 shows a general example of a short message exchange network. Inparticular, in FIG. 9, a text message is communicated between a firstcommunication device (i.e., sender 806) and a second communicationdevice (i.e., recipient 804). The sender 806 accesses a wide areanetwork (WAN) such as the Internet or the Public Telephone SwitchingNetwork (PTSN). The short message from the sender 806 via gateway 805 isdelivered to the recipient 804 via, e.g., a gateway 802 and a local areanetwork (LAN) and/or wireless network 803.

Although the recipient 804 is shown as being a mobile phone handset, therecipient 804 may comprise, e.g., a computer device connected eitherthrough the LAN 803 or via a direct modem connection to the WAN (e.g.,PTSN or the Internet) 801.

An example of a wireless short message exchange network is described inco-owned U.S. Pat. No. 6,208,870, entitled “SHORT MESSAGE SERVICENOTIFICATION IN MULTIPLE SERVICE CENTER SHORT MESSAGE SERVICE NETWORK”,the entirety of which is explicitly incorporated herein by reference.

An SMSC is a core short messaging router, which connects to the SS7public network. An SMSC provides phone-to-phone two-way messaging withinthat carrier's network, either mobile originated or mobile terminated.To provide the ability for the SMSC to communicate over the web, aWireless Internet Gateway (WIG) is added to the carrier's network. Whilean SMSC does have a direct Internet Protocol (IP) interface (i.e., ShortMessage Peer-to-Peer (SMPP)), a WIG acts as a multi-protocol router bytypically adding, e.g., six or more additional carrier-class interfaces.A WIG provides an IP based door into a carrier's network.

SMPP is typically used to provide direct communications between SMSCs.Other direct communication links used between SMSCs include CDMP, whichis MOTOROLA™ proprietary, and OIS, another proprietary protocol.

A suitable and appropriate WIG is shown and described in co-pending U.S.application Ser. No. 09/630,762, entitled “Wireless Internet Gateway”,filed Aug. 2, 2000, the entirety of which is explicitly incorporatedherein by reference.

A well known example of a system which delivers short messages is anelectronic mail system, commonly referred to as e-mail. E-mail enables asender to exchange information with a recipient from their respectivecommunication devices, e.g., typically two remotely located computerdevices.

Mobile devices such as wireless phones provide limited e-mail services.Wireless phones are designed to accept phone numbers quite easily, butare somewhat cumbersome when required to accept an alphanumeric e-mailaddress. When communicating between phone on different networks,subscribers must address messages to an e-mail address whencommunicating from phone-to-phone within the same network, only thephone number is required. Thus, text messages between wireless phones isgenerally limited in the United States to between subscribers within acommon carrier's wireless network.

With current systems, Inter-Carrier e-mail messaging (i.e., betweendifferent carrier networks) from wireless devices requires input of acomplete e-mail address. In particular, for a subscriber of a firstcarrier (“Carrier A”) to send a message to a subscriber of anothercarrier (“Carrier B”), the subscriber of Carrier A must know and input afull e-mail address of the destination device.

Exemplary full e-mail addresses typically comprise a phone number, the“@” sign, and then a unique domain name used specifically for SMSmessaging. An exemplary full e-mail address is4105551234@mobile.myportal.xyzwireless.net. A phone number onlyexperience can be provided to the subscriber of Carrier A only whensending an SMS message (e.g., e-mail) to a subscriber of the sameCarrier A.

As an example, mobile terminated short messaging is currently availablethrough web-page based services. For instance, VERIZON WIRELESS™currently maintains a web page “msg.myvzw.com” for use only by VERIZONWIRELESS™ customers. Using this web page based approach, a user insertsa phone number of a known Verizon customer, types in a body of thedesired message, and clicks on an enter key. However, this technique isavailable for mobile termination (not mobile originated) short messagesonly. Moreover, the sender must by default know to go to the Verizon webpage, and thus have advance knowledge of the particular carrierservicing a particular phone number.

Mobile originated short messaging is also available, but is cumbersometo the user and does not provide a phone number only experience. Inparticular, to send a mobile originated short message, the sender mustenter a phone number in their wireless phone, but the subscriber'snetwork will be capable of sending an associated short message only toother subscriber's within the same carrier's network. To send the shortmessage to a subscriber serviced by another carrier's network, thesubscriber must enter a complete alphanumeric e-mail address via theirmobile phone (e.g., 4105551212@mobile.att.net). As discussed, entry of alengthy list of alphanumeric characters via an alphanumeric keypad on amobile phone is cumbersome at best, particularly since several lettersare represented on any particular key, and some letters in the alphabetare not represented at all on the alphanumeric keypad.

Unfortunately, using this mobile originated technique, a sender mustknow beforehand: (1) Whether or not the subscriber is in fact on anothernetwork (thereby requiring a full e-mail address instead of just a phonenumber for in-carrier subscribers); and (2) The exact format addresssyntax of a phone number on the recipient's network (e.g.,“@mobile.att.net”.

Most carriers in other parts of the world enjoy common technologies withadjacent carriers. For instance, most carriers in Europe have a wirelessnetwork conforming to the GSM standards. Accordingly, interconnectionbetween SMSC's from different carriers is simple and straight forwardbecause they all use the same air interface (i.e., GSM). Thus, nativeSMS Inter-Carrier messaging may be accomplished through directcarrier-to-carrier interconnections. Accordingly, there is no technicalbarrier to interconnectivity, and a phone number only experience may beprovided to these GSM system subscribers using native SMS Inter-Carriermessaging which is accomplished through direct carrier-to-carrierinterconnections.

Unfortunately, the interconnection of like air interface technologies(such as GSM) is not generally an option in the US. In the US, eachmajor US carrier has deployed a different, competing air interfacetechnology (e.g., CDMA, TDMA, GSM, I-DEN (a spin-off of GSM, Motorola™proprietary), Reflex (paging networks), etc.) There are approximatelyten (10) different air interface technology protocols currently in usein the United States. While this technology dispersion allows carriersto differentiate their service offers from one another, the US consumersuffers inconvenience because of the lack of standardization and/orinteroperability across networks.

Not only is the variety of air interface technologies an integrationchallenge in the United States (many carriers espouse the superiority oftheir particular air interface technology over those provided bycompetitors), but roaming agreements for voice and SMS traffic must bereached by all potential recipients of a short message. In Europe,roaming agreements between European countries are routinely establishedbecause of the commonality of the air interface technologies (and lackof ‘technical superiority’ claims by competitors).

Practically speaking, most people remember or note down the mobile phonenumber of desired people to call. However, most people have no knowledgeof the exact carrier with which those desired people to call areserviced by. Without remembering the identity of the person's carrier, asubscriber has great difficulty in determining a full e-mail address forthat person. Without changing US society to remember not only phonenumbers of others but also which carrier each of the others are with,e-mail messaging between subscribers of different carriers will findadoption to be slow.

There is a need for providing subscribers of wireless carriers in theUnited States a phone number only experience, to facilitate and ensurethe adoption and popularity of SMS messaging in general, and e-mailmessaging in particular, in a mobile environment.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, in a messagedistribution center, a phone number only experience is provided by adatabase associating subscriber MIN numbers with servicing carriers, anda database associating carriers with routing syntax. An inter-carriermessaging module receives a digital message containing user dataaddressed with only a MIN number, performs a lookup in the databaseassociating subscriber MIN numbers and in the database associatingcarriers with routing syntax, and adds routing syntax determined fromthe lookup to the MIN number.

A method of providing a phone number only experience to a subscriber inaccordance with another aspect of the present invention comprisesreceiving an initial digital message containing user data addressed to aMIN only, and associating a carrier providing service to the MIN. A newdigital message containing user data is formulated including a body ofthe initial digital message containing user data and newly addressed tothe MIN with a syntax associated with the carrier providing service tothe MIN. The new digital message containing user data is routed.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent tothose skilled in the art from the following description with referenceto the drawings, in which:

FIGS. 1 and 2 depict a Message Distribution Center (MDC) including anInter-Carrier Messaging module including a MIN/Carrier Database and aCarrier Routing Table to provide a subscriber with “phone number only”short messaging capabilities, in accordance with the principles of thepresent invention.

FIG. 3 shows exemplary interconnections between the MDC including anInter-Carrier messaging module, and other carrier's networks usingTCP/IP protocols, in accordance with the principles of the presentinvention.

FIG. 4 shows exemplary entries in an exemplary Mobile ID Number(MIN)/Carrier Database shown in FIGS. 1 and 2.

FIG. 5 shows exemplary entries in an exemplary Carrier Routing Tableshown in FIGS. 1 and 2.

FIG. 6 depicts a phone number only experience for a subscriber ofCarrier 1 to send a short message to a subscriber of another Carrier(e.g., which does not subscribe to the Service Bureau including theInter-carrier Messaging Module), in accordance with the principles ofthe present invention.

FIG. 7 depicts a phone number only experience for a subscriber ofCarrier 1 to receive a short message from a subscriber of anotherCarrier (e.g., which does not subscribe to the Service Bureau includingthe Inter-carrier Messaging Module), in accordance with the principlesof the present invention.

FIG. 8 is an exemplary detailed “call flow” representing an IP-basedInter-Carrier Short Message Service message transaction via a MessageDistribution Center Inter-Carrier Messaging Service, in accordance withthe principles of the present invention.

FIG. 9 shows a general example of a short message exchange network.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention provides a phone number only messaging experienceto subscribing customers using native SMS Inter-Carrier Messaging, i.e.,“phone number only” messaging, as opposed to e-mail-based messaging.

An Inter-Carrier Short Messaging System (IC-SMS) service in accordancewith the principles of the present invention allows short messages to besent between networks of different technologies using only a phonenumber. Subscriber to subscriber messages are routed between carrier'snetworks by a service bureau or similar function provided by the use ofan Inter-Carrier messaging module with appropriate MIN/carrier/carrierrouting look-up capabilities.

In operation, a subscriber of the service providing an Inter-Carriermessaging module may send a mobile originated (MO) short message,addressed only with a phone number, to a subscriber in another carrier'snetwork. If in-network, the message is routed in SMSC. If notin-network, the message is sent to the ICM module. The service'sInter-Carrier messaging module determines that the destination addressof the message is not a subscriber in the sender's same network. TheInter-Carrier messaging module of the Inter-Carrier service provider(ICSP) determines the appropriate carrier for the recipient, appends theappropriate syntax to the short message to allow internet protocol (IP)or other standardized communication techniques between SMSCs of the twocarriers, and routes the short message to the destination carrier. Oncereceived, the destination carrier's network delivers the message to thefinal destination.

Furthermore, the present invention preferably allows the recipient inthe other carrier's network to reply back to the ICSP's sender back tothe sender using only the subscriber's directory number. This assists inthe provision of a phone number only experience by the ICSP'ssubscriber.

The Inter-Carrier messaging module may store an instance of theexpectation of a reply from the recipient (e.g., for a given period oftime) to allow phone number only reply's, but it is preferred that theInter-carrier messaging module simply recognize the intended recipientof a reply as being within the network of the ICSP, and effectivelystrip off any email syntax from the telephone number before forwardingthe reply short message back to the original sender.

A Message Distribution Center (MDC) including an Inter-Carrier messagingmodule in accordance with the principles of the present inventionempowers message providers (e.g.,, carriers, enterprises, webdevelopers, content providers, etc.) with a single point of entry forthe transaction of SMS messaging to a wide array of wireless networks.

The MDC including the Inter-Carrier messaging module preferably includesa carrier-grade Wireless Internet Gateway (WIG) such as the one shownand described in U.S. patent application Ser. No. 09/630,762, filed Aug.2, 2000 by Richard Smith, the entirety of which is expresslyincorporated herein by reference) in a hosted environment (e.g., aservice bureau).

An MDC Inter-Carrier SMS Service in accordance with the principles ofthe present invention provides a short message clearinghouse providingsubscribers with a capability that will enhance their communicationsfreedom through seamless, simple SMS messaging to other subscribers,regardless of the destination network.

An Inter-Carrier Messaging Service in accordance with the principles ofthe present invention is a value-added service of the MDC that allowscarriers to offer their subscribers a “phone number only” messagingexperience regardless of the destination network. The MDC Inter-CarrierMessaging Service provides protocol translation and messaging routingservice for all SMS messages terminating to addresses outside thesender's network. Additionally, the service may extend preferably thephone number only experience to mobile terminated messages that are aresult of a “reply” to a short message originated by a subscriber in thenetwork, as well as short messages originating from othercarriers/operators participating in the MDC Inter-Carrier MessagingService.

FIGS. 1 and 2 depict a Message Distribution Center (MDC) including anInter-Carrier Messaging module including a MIN/Carrier Database and aCarrier Routing Table to provide a subscriber with “phone number only”short messaging capabilities, in accordance with the principles of thepresent invention.

In particular, as shown in FIGS. 1 and 2, the MDC acts as aclearinghouse for message transactions between carrier networks.

Communication between a carrier's network and the MDC may be through theShort Message Peer to Peer (SMPP) protocol. The MDC preferably fullysupports SMPP 3.3 and 3.4 as well as other SMSC interface protocols suchas CDMP (Motorola proprietary), OIS (Sema proprietary), SNPP (pagingoperators) and WCTP (paging operators).

In FIG. 1, an MDC 200 includes an Inter-Carrier messaging module 100,MIN/Carrier database 110, and Carrier Routing Table 120, in accordancewith the principles of the present invention. The Inter-Carriermessaging module 100 enables phone number only short messaging between asubscriber's carrier 1 250 which subscribes to (or owns/maintains) theInter-Carrier service provider (ICSP) providing the Inter-Carriermessaging module 100, and subscribers 220, 230, 240 of other carrier'snetworks 260, 270, 280, respectively.

FIG. 2 shows exemplary communication protocols between the subscriber'scarrier 1 250, using e.g., SMPP, and a recipient's carrier 3 260, usinge.g., SMPP, OIS, CDMP, WCTP, SMTP, and/or HTTP. The subscriber's carrier1 250 includes an SMSC 251, MSC 252, and BS 253. Carrier 3 260 includesa Wireless Internet Gateway 271 providing access (e.g., IP protocolaccess) to an SMSC 272, MSC 273, and base station BS 274.

With respect to interoperability, at the heart of the MessageDistribution Center 200 is the carrier-proven technology of a WirelessInternet Gateway (WIG) such as that shown and described in U.S.application Ser. No. 09/630,762.

The Wireless Internet Gateway passes text messages between the Internet(via HTTP, SMTP, and other common Internet protocols) and a carrier'sShort Message Service Center (SMSC). The WIG is currently operational inmany carrier networks worldwide interoperating with SMSCs that supportSMPP, CDMP, and/or OIS protocols.

FIG. 3 shows exemplary interconnections between the MDC including anInter-Carrier messaging module, and other carrier's networks usingTCP/IP protocols, in accordance with the principles of the presentinvention.

In particular, as shown in FIG. 3, one communication method between theMDC 200 and a carrier is via SMPP or RMI, as depicted by Carrier 1,which includes a Wireless Internet Gateway 1010, SMSC 1012, STP 1014,and MSC 1016. This communication technique does not require a carrieragreement between the sending carrier and the receiving carrier, and isvery fast to market.

Alternatively, as depicted by carrier 2 in FIG. 3, an SMPP, CDMP, OIS orRMI protocol communication path may be used between the MDC 200 and theWireless Internet Gateway 1110 of the other carrier. In such a case, theWireless Internet Gateway 1110 would use SMPP, CDMP or OIS protocolcommunications with the SMSC 1112 of that carrier 2. The SMSCs 1012,1112, STPs 1014, 1114, and MSCs 1016, 1116 utilize SS7 protocols. Thissecond type carrier network supports 1-way SMS, is capable of providinga 2-way SMS, and no protocol conversion is required.

The Message Distribution Center 200 is a store and forward messagingplatform. The disclosed MDC 200 utilizes a store and forward approach toassure message delivery, complete message tracking, and maximum billingflexibility.

Most SMS service providers currently operate using open SMTP or HTTPgateways. The MDC 200 preferably provides inside-the-networkconnectivity with all the major domestic carriers and as many tier 2 and3 carriers as is feasible.

Where inside-the-network connections are unavailable, it is preferredthat open SMTP and HTTP gateway connections to carriers be used.

Preferably, the MDC 200 supports message routing to Tier 2, Tier 3 andpaging operators.

Custom control methods may be implemented to enable the MDC 200 torestrict incoming and outgoing messages to other carrier networks. Thesemethods would allow the MDC 200 to turn incoming and/or outgoingmessaging “off” on a carrier by carrier basis. Specific bounce rules anderror messages, as well as related reporting requirements, may bedefined by the operator of the MDC 200,

In addition to the above, one or more categories of “anti-spam”functionality may be defined to allow the MDC 200 to control the flow ofparticular unsolicited messages, either from a single source (e-mailaddress) or a single domain (e.g. msn.com). The MDC 200 can restrictmessages based on the following criteria a) number of allowable messagessent to a MIN in a given period of time b) number of messages sent froma particular source, including e-mail address or IP number, and c)messages with a particular subject field (e.g. “I LOVE YOU”).

In the disclosed embodiments, seven different interface methods areprovided by which SMS messages can be transmitted to wireless and pagingcarriers including SMTP, HTTP, Win Socket connection, XML RemoteProcedure Calls, SMPP and WCTP.

SMTP (Simple Mail Transport Protocol)

For developers interested in transmitting text messages using the SMTPe-mail protocol, this capability may be provided in an easy to useformat. Simplicity is the benefit of this access method. Functionality,however, is limited. This method does not allow developers to take fulladvantage of the Application Programming Interface (API)'s capability totrack a message's status or set expiration time. For more advancedcapabilities, developers must utilize one of the other interfacemethods.

HTTP (Hypertext Transport Protocol)

Messages can also be distributed to wireless devices by submittingvarious parameters for the MIN, text message, login, password, etc. to aURL. Messages can be transmitted using Secure Socket Layer (SSL) forsecure transmission to the MDC. Responses to HTTP posts can be returnedin either standard Hypertext Markup Language (HTML) or Extensible MarkupLanguage (XML) for easier data manipulation.

Win Socket Command Line

Developers may choose to interface with the MDC through a robust WinSocket Command Line interface that provides them with complete access tothe full power of the MDC's API via a Telnet session.

XML-RPC (Extensible Markup Language-Remote Procedure Calls)

XML programmers will be familiar with the XML Remote Procedure Call(XML-RPC) interface to the API. The XML-RPC interface may be imbeddedwithin an application and messages may be “posted” using the XML-RPCspecifications.

SMPP-Short Message Peer-to-Peer

The Short Message Peer to Peer protocol is an open industry standardmessaging protocol designed to simplify integration of data applicationswith wireless mobile networks. The protocol is widely deployed in themobile telecommunications industry. Currently, the MDC supports limitedSMPP functionality with complete support for SMPP 3.4 scheduled forrelease in Q3 2001.

SNPP-Simple Network Paging Protocol

The Simple Network Page Protocol is a paging industry standard messagingprotocol designed to simplify integration of data applications withpaging networks. The protocol is widely deployed within the pagingindustry.

WCTP-Wireless Communications Transfer Protocol

The Wireless Communications Transfer Protocol (WCTP) is specificallyaimed at creating an easy means of passing alphanumeric and binarymessages to and from wireline systems and two-way capable wirelessdevices. Although introduced through the paging industry, WCTP isdirectly applicable for messaging to and from most other wirelesstechnologies including PCS, GSM, and cellular.

Preferably, the MDC supports Deliver_SM and Submit_SM operations forSMPP specification versions 3.4 and 3.3, and similar operations infuture versions of SMPP, e.g., SMPP version 5.0.

The MDC's current production capacity is 80 to 100 messages/second. Atthe core of the MDC's architecture is a Wireless Internet Gateway (WIG).The WIG is a highly scalable and available carrier grade product.Preferably, the WIG architecture allows the addition of additional WIGs(as well as other network components) to increase capacity on anas-needed basis. Usage capacity may be monitored and additional capacitymay be added on an as needed basis.

Statistics used to determine latency times for the MDC include theentire time period from when a message is first received by the MDCuntil the time the MDC receives an acknowledgement that the carrier hasreceived the message. Given that assumption, the minimum latency of thedisclosed MDC is under one second, and the average latency isapproximately 2.5 seconds. The maximum latency of the MDC is essentiallyirrelevant because the longest latencies typically occur in situationswhere the destination carrier's gateway is unavailable for a period dueto problems with the carrier network. In this situation, the MDCcontinues to retry sending the message until the message expires (aconfigurable parameter) or until the carrier's gateway becomesavailable.

Multiple carrier-class Network Operating Centers (NOCs) may bemaintained throughout the country, connected via redundant T-1s andhaving mirrored applications and servers at each location.

The primary components of the MDC's application software functionsinclude protocol stacks and other interface methods that accept messagesfrom outside sources. Supported input protocols and access methodsinclude SMPP, SMTP, HTTP, WCTP, XML-RPC, and a proprietary command lineinterface accessible via a TelNet session. Other components includemessage provider validation and message tracking and billing functions,MIN destination validation functions; message queuing functions, messagerouting to destination carriers based upon MIN ranges, and outgoingmessage transmission to destination carriers (including messagethrottling based upon destination carrier's specifications).

It is preferred that most software be written in Java language, enablingportability and reuse across numerous operating environments. Thesoftware design is also preferably modular, to take advantage of RemoteMethod Invocation (RMI). RMI enables various components to bedistributed across servers increasing system performance by spreadingprocessing power across different physical servers. Furthermore, it ispreferred that the software be object oriented and multi-threaded. Asuitable database engine may be that commercially available fromORACLE™, to provide strong performance, high availability, andscalability.

FIG. 4 shows exemplary entries in an exemplary Mobile ID Number(MIN)/Carrier Database 110 shown in FIGS. 1 and 2.

In particular, as depicted in FIG. 4, a first entry 310 includes anassociation between the MIN (i.e., phone number) 410-555-1212, and itscarrier, AT&T™. The second entry 320 indicates that the phone number410-123-4567 is serviced by Verizon™, and the third entry 330 indicatesthat a fourth MIN 212-654-3210 is serviced by Sprint™.

Preferably, the entries in the MIN/Carrier database may encompass agreat majority of all MINs. For instance, in the preferred embodiment,the MIN/Carrier database 110 is filled with information from the FCCmandated Local Exchange Registry (LER) which currently includesapproximately 85% of the MINs in use in the United States. Of course,those MINs may be augmented as necessary or desired with MINs nototherwise in the LER, within the principles of the present invention.

FIG. 5 shows exemplary entries in an exemplary Carrier Routing Table 120shown in FIGS. 1 and 2.

In particular, as shown in FIG. 5, a first entry 488 indicates thatcommunication between the Inter-Carrier service provider (ICSP) and thecarrier “AT&T” is by SMTP protocol (i.e., e-mail), and that the phonenumber only short messages received for delivery to AT&T should beappended with the syntax “@mobile.att.net”. A second entry 489 indicatesthat communication between the ICSP and the carrier “Verizon” is by SMTPprotocol, and that short messages send with phone number only should beappended with the syntax “@mobile.myportal.xyzwireless.net”.

The exemplary carrier routing table 120 shown in FIG. 5 may be extendedto include a country of the carrier, allowing inclusion of necessarysyntax (e.g., a country code appended to an email address), use ofparticular communication links, etc.

The advantages of a phone number only short messaging experience inaccordance with the principles of the present invention can be readilyappreciated when considering the alternatives (presuming that the senderknows the particular carrier associated with a recipient's phone number)of manual entry of the syntaxes such as“@mobile.myportal.xyzwireless.net”.

FIG. 6 depicts a phone number only experience for a subscriber 210 ofCarrier 1 250 to send a short message to a subscriber 500 of a differentCarrier 2 270 (e.g., which does not subscribe to the ICSP (i.e., ServiceBureau) including the Inter-carrier Messaging Module). In particular, asshown in FIG. 6, the subscriber 210 need only send a short message usingthe simple phone number 410-555-1234 of subscriber 500, with theInter-Carrier messaging module 100 automatically determining the carrierprovider servicing subscriber 500, the method of communication betweenthe Inter-Carrier messaging module 100 of the MDC 200 and the carrier 2270, and then adding (e.g., appending) the appropriate syntax to thephone number to actually address the short message to “410-555-1234”.

In accordance with the principles of the present invention, the shortmessage sent by subscriber 210 to subscriber 555 is preferably sent withthe sender's address in phone number only form, to facilitate the replyof a phone number only short message back to the original subscriber210. However, the present invention preferably accommodates reply shortmessages (and/or new short messages) to a subscriber 210 using the full,formal SMTP address such as “443-994-9854@mdc.carrier-1.net”.

While the embodiments of the present invention relate to the addition ofsyntax to the end of a phone number (i.e., appending the syntax), thepresent invention relates equally to the addition of a prefix to thephone number, the insertion of syntax information within the phonenumber, and/or to the addition of suffix information at the end of thephone number.

FIG. 7 depicts a phone number only experience for a subscriber 210 ofCarrier 1 250 to receive a short message from a subscriber 500 ofanother Carrier 2 270, e.g., which does not subscribe to the ICSP orService Bureau including the Inter-carrier Messaging Module 100 inaccordance with the principles of the present invention.

In particular, subscriber 500 sends a short message addressed to4439949854@mdc.carrier-1.net. This would conventionally arrive at thesubscriber's mobile phone 210 indicating a source using more than simplya phone number, which violates the preferred embodiments of the presentinvention wherein a clean phone number only experience is desired.

To provide a phone number only experience in accordance with the presentembodiment, the short message to subscriber 210 is routed through theInter-Carrier messaging module 100, where the syntax in the sourceaddress of the short message is stripped down preferably to only thephone number. In this way, the subscriber 210 sees a short message whichappears to them to have been sent by “4105551234”.

In operation, with reference to FIG. 1, Carrier 1 250 receives a shortmessage from a subscriber 210 with a destination address of a phonenumber only (i.e., MIN). The SMSC of the Carrier 250 reviews theintended destination of the short message. If the Carrier 250 does notrecognize the phone number as being another subscriber of the Carrier250, then the Carrier 250 dumps the short message with the phone numberto the Inter-Carrier Messaging Module 100 of the MDC 200 over, e.g., anSMPP communication pathway.

The Inter-Carrier Messaging Module 100 accesses the MIN/Carrier database110 to perform a MIN database lookup, which returns with the name of thecarrier (e.g., Verizon) providing service to that phone number.

Thereafter, the Inter-Carrier Messaging Module 100 accesses the CarrierRouting Table 120 to determine how the MDC 200 communicates with theparticular carrier returned from the MIN/Carrier database lookup (e.g.,SMTP). Moreover, the Carrier Routing Table 120 also preferably returnsthe appropriate syntax to add to the phone number to properly route theshort message (e.g., “@msg.myvzw.com”)

With the appropriate syntax now in hand, the Inter-Carrier MessagingModule 100 assembles a new short message, including the phone numberwith syntax added (e.g., 4107033375@msg.myvzw.com), the body of theshort message, the originator address, and optional parameters such aspriority, expiration, etc.

Inclusion of the source address (i.e., phone number) provides therecipient with the ability to reply to the received short message. Thesource address could include the full address of the source, includingboth the phone number and the appropriate syntax, but this would resultin a possible reply short message which would violate the desired phonenumber only experience for subscribers of certain carriers. Therefore,preferably, the source address in the originally sent short message isadded such that any reply short message would be forced back through theMDC 200 including the Inter-Carrier Messaging Module, which wouldrecognize the phone number of the new recipient, and would forward theshort message with the syntax stripped off.

For instance, the source address of the original short message can beset at the phone number of the subscriber 210, together with the syntaxof the MDC 200 (e.g., 4439110002@mdc.att.net). The Inter-CarrierMessaging Module 100 would copy the body of the reply short messagecoming from the non-subscribing carrier (i.e., with syntax included inthe destination address), apply the optional parameters, perform anotherMIN table lookup, and routing table lookup, thus formulating a new shortmessage, and deliver the reply short message back to the subscriber 210of the customer carrier 250.

FIG. 8 is an exemplary detailed “call flow” representing an IP-basedInter-Carrier Short Message Service message transaction via a MessageDistribution Center Inter-Carrier Messaging Service, in accordance withthe principles of the present invention.

Step 700: Subscriber A originates a message to Subscriber B from their2-way Messaging Device. The message is addressed to Subscriber B's phonenumber (i.e., to the subscriber's Mobile Identification Number (MIN)only.

Step 702: Carrier A's network elements identify non-Carrier A addressesand forwards them to the MDC via, e.g., SMPP, CDMP, OIS, HypertextTransfer Protocol (HTTP)(i.e., the web), SMTP (i.e., e-mail), WirelessCommunications Transport Protocol (WCTP)(i.e., paging networks), SimpleNetwork Paging Protocol (SNPP), XML-RPC or TCP/IP socket API.

Step 704, or 706 or 708: As the MDC receives the message from Carrier A,it first determines the destination carrier (Carrier B) as well as theprotocol supported by Carrier B. Then the MDC appends the MDC/Carrier Adomain (mdc.carrier-a.net in the diagram) to Subscriber A's phone numberand routes the message accordingly.

Step 710: Carrier B's wireless Internet gateway routes the message tocarrier B's own SMSC.

Step 720: SMSC of Carrier B delivers message to subscriber B's 2-waymessaging device via appropriate air interface (e.g., over an SS7 link).

Step 730: Subscriber B replies to the message. The message is routed toCarrier B's SMSC via appropriate air interface (e.g., over an SS7 link).

Step 740, 760 and 780: Depending upon the type of relationship enjoyedwith the Carrier B, messages are either transported directly fromCarrier B's SMSC to the MDC using SMPP (or other protocol) OR they aredirected to Carrier B's Internet gateway using SMPP (or other protocol)and then onto the MDC using SMTP or HTTP.

Step 782: The MDC receives a mobile originated message from Carrier Breplying to the original message. The MDC routes the message to CarrierA's network.

Step 784: Carrier A's network receives the message and forwards it toSubscriber A's 2-Way Messaging Device.

Another function of the call flow shown in FIG. 8 is that it allows fordelivery receipt notification between Carrier A's devices and CarrierB's devices which support delivery receipts.

Through the Message Linking feature, the MDC 200 determines the lengthof message supported by Carrier B and, if necessary, breaks lengthymessages into multiple linked messages.

The present invention allows 2-way pagers with querty keyboards to sendshort messages using phone number only addressing to any mobile phone(or to any other pager).

The phone number only capabilities of an Inter-Carrier Messaging Moduleand associated databases in accordance with the principles of thepresent invention has the capability to bridge non-SMS messagingdevices, e.g., ReFlex and Mobitex pagers.

The present invention provides multiple benefits. For instance, simple“phone number only” SMS messaging across major carrier networks will addsignificantly to the continued adoption of SMS messaging particularly inthe United States. Additionally, carriers can structure their pricingplans to recognize additional revenue from Inter-Carrier messagesthrough the control and management of Inter-Carrier Messaging inaccordance with the principles of the present invention.

Moreover, the present invention provides SMS traffic management andcontrol, and a potential additional revenue stream for a carrier frominternational messaging.

The invention has particular use with respect to cellular and PCScarriers, and paging network operators (e.g., Verizon Wireless, AT&TWireless, Sprint PCS, VoiceStream, SkyTel, etc.) in North America aswell as other markets served by operators employing disparate airinterface technologies.

While the invention has been described with reference to the exemplaryembodiments thereof, those skilled in the art will be able to makevarious modifications to the described embodiments of the inventionwithout departing from the true spirit and scope of the invention.

What is claimed is:
 1. A system for processing a short message addressedwith a number only, comprising: an access module to access a firstdatabase associating subscriber MIN numbers with a plurality ofcorresponding servicing carriers and a second database associating saidplurality of corresponding servicing carriers and corresponding routingsyntax; an inter-carrier messaging module to receive a short message, toperform a lookup of said particular subscriber MIN in said firstdatabase, to perform a lookup of a retrieved particular servicingcarrier in said second database to retrieve a particular routing syntax,and to add said particular routing syntax to said short message; and atransmitter to transmit said short message including a source deviceidentified with only a MIN number.
 2. A system for processing a shortmessage addressed with a number only according to claim 1, wherein: saidfirst database and said database are in a common database.
 3. A systemfor processing a short message addressed with a number only according toclaim 1, wherein: said MIN is a phone number.
 4. A system for processinga short message addressed with a number only according to claim 1,wherein: said system forms a store and forward short messaging platform.5. A system for processing a short message addressed with a number onlyaccording to claim 1, wherein: said short message is received at androuted from, a service bureau.
 6. A system for processing a shortmessage addressed with a number only according to claim 1, wherein: saidshort message with said added particular routing syntax forms a routableaddress.
 7. A system for processing a short message addressed with anumber only according to claim 1, wherein: said routable address is ane-mail address.
 8. A method for processing a short message addressedwith a number only, comprising the steps of: receiving, at aninter-carrier messaging module, a short message; performing a lookup ina first database associating subscriber MIN numbers with a plurality ofcorresponding servicing carriers and performing a lookup of a retrievedparticular servicing carrier in said second database to retrieve aparticular routing syntax; adding said particular routing syntax to saidshort message; and transmitting said short message including a sourcedevice identified with only a MIN number.
 9. The method for processing ashort message addressed with a number only according to claim 8, furthercomprising: receiving and routing said short message to and from aservice bureau.
 10. The method for processing a short message addressedwith a number only according to claim 8, wherein: said MIN is a phonenumber.
 11. The method for processing a short message addressed with anumber only according to claim 8, wherein: forming a routable addresswith said MIN and said added particular routing syntax.
 12. The methodfor processing a short message addressed with a number only according toclaim 11, wherein: said routable address is an e-mail address.
 13. Amethod of directing a data message from a first device to a seconddevice, comprising: receiving a data message, addressed with only adestination device phone number associated with a second carrier, from asource device associated with a first carrier; transmitting said datamessage, addressed with only a source device phone number identifyingsaid source device, from a message distribution center associatingappropriate routing syntax with said destination device phone number;and routing said data message to a destination device associated withsaid destination device phone number using said appropriate routingsyntax, said destination device being serviced by a second carrierdifferent from said first carrier.
 14. The method of directing a datamessage from a first device to a second device according to claim 13,comprising: routing a return message from said destination device backto said source device using only said source device phone number. 15.The method of directing a data message from a first device to a seconddevice according to claim 13, comprising: said data message istransmitted wirelessly.
 16. The method of directing a data message froma first device to a second device according to claim 13, wherein saidappropriate routing syntax comprises: said destination device phonenumber; and a routable address within said second carrier's network. 17.The method of directing a data message from a first device to a seconddevice according to claim 16, comprising: said routable address is anemail address.
 18. The method of directing a data message from a firstdevice to a second device according to claim 13, comprising: said datamessage is routed via an Internet.
 19. Apparatus for directing a datamessage from a first device to a second device, comprising: a receiver,at a physical distribution center, to receive a data message, addressedwith only a destination device phone number associated with a secondcarrier, from a source device associated with a first carrier; atransmitter, at said physical distribution center, to transmit said datamessage, addressed with only a source device phone number identifyingsaid source device, from said physical distribution center, associatingappropriate routing syntax with said destination device phone number;and a router, at said physical distribution center, to route said datamessage to said destination device using said appropriate routingsyntax.
 20. The apparatus for directing a data message from a firstdevice to a second device according to claim 19, wherein said routerfurther: routes a return message from said destination device back tosaid source device using only said source device phone number.
 21. Theapparatus for directing a data message from a first device to a seconddevice according to claim 19, comprising: said data message is awireless data message.
 22. The apparatus for directing a data messagefrom a first device to a second device according to claim 19, wherein:said router routes said data message from said physical distributioncenter.
 23. The apparatus for directing a data message from a firstdevice to a second device according to claim 19, wherein saidappropriate routing syntax comprises: said destination device phonenumber; and a routable address within a network of said second carrier.24. The apparatus for directing a data message from a first device to asecond device according to claim 23, comprising: said routable addressis an email address.
 25. The apparatus for directing a data message froma first device to a second device according to claim 19, comprising:said data message is routed via an Internet.